[blog] Announce JS SDK 2.0 #6574

JamieDanielson · 2025-03-19T18:48:02Z

OpenTelemetry JavaScript recently released SDK 2.0. There have been many improvements and breaking changes and we want to make this easily findable.

Preview: https://deploy-preview-6574--opentelemetry.netlify.app/blog/2025/otel-js-sdk-2-0/

maryliag · 2025-03-19T19:07:05Z

content/en/blog/2025/otel-js-sdk-2-0.md

+  [v2.0.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0)
+  and
+  [v0.200.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.200.0)
+  releases and provide feedback


do you want to add something on how to provide feedback? I see people getting confused on how to do so. Maybe mention creation of issues, or reaching our slack/SIG. I know you added slack and sig right below, but wanted to make more clear those are the communications channels for feedback too

The upgrade guide has this blurb, FWIW:

If you have any questions about the 2.x changes, please ask! You can reach the OTel JS community on the [#otel-js](https://cloud-native.slack.com/archives/C01NL1GRPQR) channel of the [CNCF Slack](https://slack.cncf.io/), [open a Discussion issue](https://github.com/open-telemetry/opentelemetry-js/issues/new?template=discussion.md) on the repository, or join the weekly [OTel JS SIG zoom call](https://docs.google.com/document/d/1tCyoQK49WVcE-x8oryZOTTToFm7sIeUhxFPm9g-qL1k/edit).

If you have any questions about the 2.x changes, please ask! You can reach the OTel JS community on the #otel-js channel of the CNCF Slack, open a Discussion issue on the repository, or join the weekly OTel JS SIG zoom call.

Oh... I guess the subsequent few bullets include links on how to get involved.

trentm

Nice. LGTM.

content/en/blog/2025/otel-js-sdk-2-0.md

chalin · 2025-03-20T09:48:35Z

content/en/blog/2025/otel-js-sdk-2-0.md

+---
+title: Announcing the OpenTelemetry JavaScript SDK 2.0
+linkTitle: OTel JS SDK 2.0
+date: 2025-02-21


Suggested change

date: 2025-02-21

date: 2025-02-20

content/en/blog/2025/otel-js-sdk-2-0.md

chalin

Great to see a blog post about the new release. See inline comments for preliminary suggestions.

content/en/blog/2025/otel-js-sdk-2-0.md

chalin · 2025-03-20T10:10:29Z

/fix:refcache

opentelemetrybot · 2025-03-20T10:10:51Z

You triggered fix:refcache action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/13966803156

opentelemetrybot · 2025-03-20T10:16:26Z

fix:refcache was successful.

IMPORTANT: (RE-)RUN `/fix:all` to ensure that there are no remaining check issues.

chalin · 2025-03-20T10:18:33Z

FYI, related concern:

Publish "Upgrade to OpenTelemetry JS SDK 2.x" to the OTel website #6579

chalin · 2025-03-21T18:56:54Z

@JamieDanielson @open-telemetry/javascript-approvers - I'm curious, what is your ETA for finalization of this post?

JamieDanielson · 2025-03-21T19:20:57Z

@JamieDanielson @open-telemetry/javascript-approvers - I'm curious, what is your ETA for finalization of this post?

I am heading out of town for the weekend. I committed a few suggestions, and if anyone has other ideas on what else to add please do so! I think this should be ready to go.

chalin · 2025-03-21T19:22:02Z

/fix:all

opentelemetrybot · 2025-03-21T19:22:16Z

You triggered fix:all action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/13999356748

opentelemetrybot · 2025-03-21T19:28:30Z

fix:all was successful.

IMPORTANT: (RE-)RUN `/fix:all` to ensure that there are no remaining check issues.

Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com>

chalin · 2025-03-21T23:16:49Z

content/en/blog/2025/otel-js-sdk-2-0.md

+
+## What has changed?
+
+### Summary


There isn't enough content to justify section headings IMHO. Let's inline these a paragraphs:

Suggested change

### Summary

In summary:

chalin · 2025-03-21T23:17:02Z

content/en/blog/2025/otel-js-sdk-2-0.md

+  - for notes on migrating to 2.x / 0.200.x see
+    [the upgrade guide](https://github.com/open-telemetry/opentelemetry-js/tree/main/doc/upgrade-to-2.x.md)
+
+### Details


Suggested change

### Details

Details:

chalin · 2025-03-21T23:20:28Z

content/en/blog/2025/otel-js-sdk-2-0.md

+Some of the details for why this 2.0 was done can be found
+[in this issue](https://github.com/open-telemetry/opentelemetry-js/issues/4083).
+We knew we would gain the greatest benefit by allowing breaking changes to
+improve things related to:
+
+- Optimization: removing classes and namespaces to allow better minification and
+  tree-shaking.
+- Better Tooling and Support: dropping old runtimes and tool versions to take
+  advantage of enhanced ESM support and simplify documentation.
+- Velocity: reducing code complexity and removing deprecated fields for faster
+  feature and maintenance work.
+
+This also begins our goal of releasing a new major release every year.


Move the "for more details" to the end of the post:

Suggested change

Some of the details for why this 2.0 was done can be found

[in this issue](https://github.com/open-telemetry/opentelemetry-js/issues/4083).

We knew we would gain the greatest benefit by allowing breaking changes to

improve things related to:

- Optimization: removing classes and namespaces to allow better minification and

tree-shaking.

- Better Tooling and Support: dropping old runtimes and tool versions to take

advantage of enhanced ESM support and simplify documentation.

- Velocity: reducing code complexity and removing deprecated fields for faster

feature and maintenance work.

This also begins our goal of releasing a new major release every year.

We knew we would gain the greatest benefit by allowing breaking changes to

improve things related to:

- Optimization: removing classes and namespaces to allow better minification and

tree-shaking.

- Better Tooling and Support: dropping old runtimes and tool versions to take

advantage of enhanced ESM support and simplify documentation.

- Velocity: reducing code complexity and removing deprecated fields for faster

feature and maintenance work.

This also begins our goal of releasing a new major release every year.

For a more detailed explanation of why 2.0, see issue [#4083].

[#4083]: https://github.com/open-telemetry/opentelemetry-js/issues/4083

chalin · 2025-03-21T23:22:59Z

content/en/blog/2025/otel-js-sdk-2-0.md

+Exciting news: [OpenTelemetry JavaScript](/docs/languages/js/) has released
+[SDK 2.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0)!


Suggested change

Exciting news: [OpenTelemetry JavaScript](/docs/languages/js/) has released

[SDK 2.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0)!

Exciting news: [OpenTelemetry JavaScript](/docs/languages/js/) has released [SDK

2.0][v2.0.0]!

[v2.0.0]: https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0

FYI: the same link definition is used further below in another suggestion.

chalin · 2025-03-21T23:25:45Z

content/en/blog/2025/otel-js-sdk-2-0.md

+- Try out the
+  [v2.0.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0)
+  and
+  [v0.200.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.200.0)
+  releases and provide feedback


Suggested change

- Try out the

[v2.0.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0)

and

[v0.200.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.200.0)

releases and provide feedback

[v0.200.0]:

https://github.com/open-telemetry/opentelemetry-js/releases/tag/experimental%2Fv0.200.0

- Try out the [v2.0.0] and [v0.200.0] releases and provide feedback

opentelemetrybot requested a review from a team March 19, 2025 18:48

github-actions bot added the blog label Mar 19, 2025

JamieDanielson requested review from a team and maryliag and removed request for a team March 19, 2025 18:48

opentelemetrybot requested a review from a team March 19, 2025 18:52

maryliag reviewed Mar 19, 2025

View reviewed changes

trentm approved these changes Mar 19, 2025

View reviewed changes

chalin reviewed Mar 20, 2025

View reviewed changes

content/en/blog/2025/otel-js-sdk-2-0.md Outdated Show resolved Hide resolved

opentelemetrybot requested a review from a team March 20, 2025 09:47

chalin reviewed Mar 20, 2025

View reviewed changes

opentelemetrybot requested a review from a team March 20, 2025 09:52

chalin reviewed Mar 20, 2025

View reviewed changes

chalin mentioned this pull request Mar 20, 2025

Publish "Upgrade to OpenTelemetry JS SDK 2.x" to the OTel website #6579

Open

chalin mentioned this pull request Mar 20, 2025

Add nudge to PR actions #6578

Open

chalin force-pushed the jamie.blog-oteljs-sdk-2-0 branch from 9d7e359 to d0359b8 Compare March 20, 2025 10:47

opentelemetrybot requested a review from a team March 20, 2025 10:47

JamieDanielson marked this pull request as ready for review March 21, 2025 19:18

JamieDanielson requested a review from a team as a code owner March 21, 2025 19:18

JamieDanielson added 2 commits March 21, 2025 15:31

blog[js]: Add post announcing JS SDK 2.0

9a093bd

fixins

518de45

JamieDanielson and others added 7 commits March 21, 2025 15:31

ignore me

ab1f5ce

another fix it seems

a12b6c6

Set draft status

3e4a719

Fix date

5c3ac24

Results from /fix:refcache

dbce1c7

Apply suggestions from code review

e09db90

Co-authored-by: Patrice Chalin <chalin@users.noreply.github.com>

Results from /fix:all

bcc6a27

chalin force-pushed the jamie.blog-oteljs-sdk-2-0 branch from 719e321 to bcc6a27 Compare March 21, 2025 19:31

chalin changed the title ~~blog[js]: Add post announcing JS SDK 2.0~~ [blog] Announce JS SDK 2.0 Mar 21, 2025

maryliag approved these changes Mar 21, 2025

View reviewed changes

chalin reviewed Mar 21, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[blog] Announce JS SDK 2.0 #6574

[blog] Announce JS SDK 2.0 #6574

JamieDanielson commented Mar 19, 2025 •

edited by chalin

Loading

maryliag Mar 19, 2025

trentm Mar 19, 2025 •

edited

Loading

trentm Mar 19, 2025

trentm left a comment

chalin Mar 20, 2025

chalin left a comment

chalin commented Mar 20, 2025

opentelemetrybot commented Mar 20, 2025

opentelemetrybot commented Mar 20, 2025

chalin commented Mar 20, 2025

chalin commented Mar 21, 2025

JamieDanielson commented Mar 21, 2025

chalin commented Mar 21, 2025

opentelemetrybot commented Mar 21, 2025

opentelemetrybot commented Mar 21, 2025

chalin Mar 21, 2025 •

edited

Loading

chalin Mar 21, 2025

chalin Mar 21, 2025

chalin Mar 21, 2025

chalin Mar 21, 2025

		Exciting news: [OpenTelemetry JavaScript](/docs/languages/js/) has released
		[SDK 2.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0)!

-Exciting news: [OpenTelemetry JavaScript](/docs/languages/js/) has released
-[SDK 2.0](https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0)!
+Exciting news: [OpenTelemetry JavaScript](/docs/languages/js/) has released [SDK
+.0][v2.0.0]!
+[v2.0.0]: https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0

[blog] Announce JS SDK 2.0 #6574

Are you sure you want to change the base?

[blog] Announce JS SDK 2.0 #6574

Conversation

JamieDanielson commented Mar 19, 2025 • edited by chalin Loading

maryliag Mar 19, 2025

Choose a reason for hiding this comment

trentm Mar 19, 2025 • edited Loading

Choose a reason for hiding this comment

trentm Mar 19, 2025

Choose a reason for hiding this comment

trentm left a comment

Choose a reason for hiding this comment

chalin Mar 20, 2025

Choose a reason for hiding this comment

chalin left a comment

Choose a reason for hiding this comment

chalin commented Mar 20, 2025

opentelemetrybot commented Mar 20, 2025

opentelemetrybot commented Mar 20, 2025

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

chalin commented Mar 20, 2025

chalin commented Mar 21, 2025

JamieDanielson commented Mar 21, 2025

chalin commented Mar 21, 2025

opentelemetrybot commented Mar 21, 2025

opentelemetrybot commented Mar 21, 2025

IMPORTANT: (RE-)RUN /fix:all to ensure that there are no remaining check issues.

chalin Mar 21, 2025 • edited Loading

Choose a reason for hiding this comment

chalin Mar 21, 2025

Choose a reason for hiding this comment

chalin Mar 21, 2025

Choose a reason for hiding this comment

chalin Mar 21, 2025

Choose a reason for hiding this comment

chalin Mar 21, 2025

Choose a reason for hiding this comment

JamieDanielson commented Mar 19, 2025 •

edited by chalin

Loading

trentm Mar 19, 2025 •

edited

Loading

IMPORTANT: (RE-)RUN `/fix:all` to ensure that there are no remaining check issues.

IMPORTANT: (RE-)RUN `/fix:all` to ensure that there are no remaining check issues.

chalin Mar 21, 2025 •

edited

Loading